Ping.

@mgorny Ooops I missed this. Why do I need this? AFAIK there's no place where I set SETUPPY_FORCE_PURE for tests.

Downstreams use SETUPPY_FORCE_PURE to build pure Python version of the package, and then the test suite fails.

I just want to understand why anyone would repackage this as pure-python in a downstream. Which distros? Some details?

Gentoo. We give our users an option to disable all C extensions, if they wish. However, in my case the primary use is comparing behavior of the same module on PyPy (where there is no C extension ever) and CPython. By building the package on CPython without the extension modules, I have fewer differences to be concerned about, and therefore it is easier to determine whether the particular problem is specific to PyPy or perhaps to the use of pure Python code paths.

Thank you!